Pass request_context to resolvers as a context value #19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ciscorn
commented
Aug 23, 2018
|
Is there any chance of this getting merged? This is blocking me, as there's no way to pass the request to a resolver. |
|
@subwindow
@Cito is working on graphql-ws-next, hopefully will be published soon. In the meantime you can "monkeypatch" this library - see #7 (comment) or the same thing in my demo project. |
|
Awesome, that worked. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Request objects should be accessible via
info.context, like sanic-graphql, aiohttp-graphql, etc.